This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
docs: warn that useState should only contain JSON-serializable content
#5994
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
β Deploy Preview for nuxt3-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
7 tasks
Co-authored-by: Damian GΕowala <48835293+DamianGlowala@users.noreply.github.com>
|
@danielroe Do you mind to simplify the explanation to be similar to the guide page? #5994 (comment) |
danielroe
commented
Jul 21, 2022
danielroe
commented
Jul 21, 2022
pi0
reviewed
Jul 21, 2022
pi0
approved these changes
Jul 21, 2022
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
resolves nuxt/nuxt#14326.
β Type of change
π Description
Adds a brief warning about serializable content in
useState. I haven't added similar warnings to data fetching composables as this is less likely to be an issue given that is originally coming over the wire as JSON, most likely, but I may change my mind, and happy to be convinced otherwise.π Checklist